<?php
/**
 * <https://y.st./>
 * Copyright © 2017 Alex Yst <mailto:copyright@y.st>
 * 
 * This program is free software: you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, either version 3 of the License, or
 * (at your option) any later version.
 * 
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
 * GNU General Public License for more details.
 * 
 * You should have received a copy of the GNU General Public License
 * along with this program. If not, see <https://www.gnu.org./licenses/>.
**/

$xhtml = array(
	'<{title}>' => 'Wix',
	'<{subtitle}>' => 'Written in <span title="Web Programming 1">CS 2205</span> of <a href="http://www.uopeople.edu/">University of the People</a>, finalised on 2017-09-20',
	'<{copyright year}>' => '2017',
	'takedown' => '2017-11-01',
	'<{body}>' => <<<END
<p>
	We were required to use Wix to produce our website this week, and I needed a topic for the website. I find Wix to be incredibly painful to work with. It&apos;s inflexible and doesn&apos;t allow direct editing of the $a[XHTML]/$a[HTML]. Seeing as I think the Wix system is not very functional and I needed a topic, that&apos;s the topic I went with.
</p>
<p>
	As per the assignment instructions, there are five pages, five images, a navigation menu present on all pages, and at least one hundred words on each page. I write in English English (from actual England, known more formally as the United Kingdom), which differs from United States English a bit. Everything is spelled correctly, so if you think I made a spelling error, please first verify that it&apos;s actually misspelled and not just a differently-spelled word before marking me down.
</p>
<p>
	The website I built for this assignment is at <a href="#home"><code>#home</code></a>.
</p>
<hr/>
<section id="home">
	<nav>
		<ul>
			<li>
				<a href="#home">Home</a>
			</li>
			<li>
				<a href="#xhtml">No XHTML access</a>
			</li>
			<li>
				<a href="#javascript">Required JavaScript</a>
			</li>
			<li>
				<a href="#menus">Tall menus</a>
			</li>
			<li>
				<a href="#good-things">Good things about Wix</a>
			</li>
			<li>
				<a href="https://y.st./en/coursework/">Past coursework</a>
			</li>
		</ul>
	</nav>
	<h2>CS 2205 (Web Programming 1) Unit 2</h2>
	<img src="/img/CC_BY-SA_4.0/y.st./coursework/CS2205/IMG_20170920_114441.jpg" alt="Purple flowers with white speckles" class="framed-centred-image" width="800" height="480"/>
	<p>
		This website was created to fulfil the requirements of the CS 2205 (Web Programming 1) Unit 2 assignment at University of the people.
		I want to thank the Wix team for providing a gratis Web platform for us students to work with, but at the same time, the Wix platform is incredibly inflexible and painful to use.
		It is my hope that a member of the Wix team, if they look over this website, will take the criticism offered well and will use it to better the platform.
		I don&apos;t mean to be mean, but the Wix system isn&apos;t fit for use in building serious websites in its current state.
		I mean, with Wix, you don&apos;t even get an index page.
		If you try to load the root page of the website, you get a 404 error!
	</p>
	<p>
		Normally, I archive an exact copy of all my coursework submissions on my main website.
		However, a Wix-powered monstrosity is just of too low of quality to be worth saving.
		I ended up keeping a stripped-down, single-page version instead.
	</p>
</section>
<hr/>
<section id="xhtml">
	<nav>
		<ul>
			<li>
				<a href="#home">Home</a>
			</li>
			<li>
				<a href="#xhtml">No XHTML access</a>
			</li>
			<li>
				<a href="#javascript">Required JavaScript</a>
			</li>
			<li>
				<a href="#menus">Tall menus</a>
			</li>
			<li>
				<a href="#good-things">Good things about Wix</a>
			</li>
			<li>
				<a href="https://y.st./en/coursework/">Past coursework</a>
			</li>
		</ul>
	</nav>
	<h2>No XHTML access</h2>
	<img src="/img/CC_BY-SA_4.0/y.st./coursework/CS2205/IMG_20170920_114535.jpg" alt="Purple, triangular leaves" class="framed-centred-image" width="800" height="480"/>
	<p>
		Wix doesn&apos;t allow access to the XHTML code for editing.
		This makes working with Wix incredibly painful for a Web developer that actually knows what they&apos;re doing.
		In XHTML or HTML, you can create any page within the range of possible Web pages.
		However, a graphical interface offers only a fraction of that capability.
		To be clear, it&apos;s not a problem that Wix offers a graphical interface.
		That can be incredibly useful for those that need or want it.
		However, there should always be the option to either write the page from scratch in XHTML/HTML, or at the very least, clean up the XHTML code of a GUI-created page.
		Without that option, Wix is unfit for use in building any serious website.
	</p>
	<p>
		I couldn&apos;t even find a way to get basic <abbr/> elements inserted into my paragraphs.
		Wix&apos;s graphical interface just doesn&apos;t offer that option, but if they additionally offered an XHTML-/HTML-editing option, adding these elements would&apos;ve been a breeze!
	</p>
	<p>
		Wix doesn&apos;t even offer a basic file-upload dialogue.
		The only option they provide for uploading images is drag-and-drop, which quite frankly, is a pain in the butt.
		You have to locate the images in your file manager, make sure the Web browser is open behind the file manager, then drag.
		This is pointlessly obtuse.
		I have four desktops, and my file manager is usually on a different desktop than my Web browser.
		It&apos;s fine for people that want it, but it certainly shouldn&apos;t be the *only* method of uploading files.
		An amateur could build a better interface than this by simply using the same basic code that almost every other website uses for file uploads.
	</p>
</section>
<hr/>
<section id="javascript">
	<nav>
		<ul>
			<li>
				<a href="#home">Home</a>
			</li>
			<li>
				<a href="#xhtml">No XHTML access</a>
			</li>
			<li>
				<a href="#javascript">Required JavaScript</a>
			</li>
			<li>
				<a href="#menus">Tall menus</a>
			</li>
			<li>
				<a href="#good-things">Good things about Wix</a>
			</li>
			<li>
				<a href="https://y.st./en/coursework/">Past coursework</a>
			</li>
		</ul>
	</nav>
	<h2>Required JavaScript</h2>
	<img src="/img/CC_BY-SA_4.0/y.st./coursework/CS2205/IMG_20170920_114603.jpg" alt="A rose in bloom" class="framed-centred-image" width="800" height="480"/>
	<p>
		There are many reasons a user might keep JavaScript disabled in their Web browsers.
		For me, I disable JavaScript because of my school&apos;s website.
		University of the People&apos;s classroom website, known to its students as &quot;Moodle&quot;, has a tendency to lock up.
		Repeatedly.
		While typing in the text fields, the entire page will often stop responding entirely, so partial words, whole words, or even entire sentences I type are lost.
		It&apos;s a major hassle, and University of the People representatives deny the presence of the problem.
		I&apos;m no expert, but the people I&apos;ve talked to outside the school about the problem blame poorly-timed AJAX requests.
		Seriously, AJAX requests should <strong>*not*</strong> be made when the user is typing instead of clicking buttons.
		If a page-altering button isn&apos;t clicked, no AJAX requests should be being made.
		I&apos;ve found though that by disabling JavaScript, the website not only stops locking up, but the text-input fields function in a much more streamlined way for my workflow.
		With JavaScript enabled, it takes two clicks to switch the text areas from rich text mode to XHTML mode.
		This is a decent default for most people.
		With JavaScript disabled though, the text areas instead operate as XHTML input fields right off the bat with no extra clicking.
		For me personally, as I compose nearly everything in XHTML, this is a more convenient default.
	</p>
	<p>
		The Wix system doesn&apos;t function without JavaScript enabled though, due to its entirely-graphical interface.
		If Wix provided a option to input XHTML or HTML directly, that functionality could much more easily be provided with a basic HTTP POST form with no JavaScript required.
		The graphical editor built in JavaScript in nice for some, but there should really be another option for those that don&apos;t have JavaScript enabled or don&apos;t have a JavaScript-capable Web browser.
		Once JavaScript is enabled, the system functions, but really slowly.
		It took several times the amount of time it should have to construct a site using Wix.
		This also means that you can&apos;t work offline, then upload when you get a chance.
		You *must* be on the web to build a Wix website, and there&apos;s no way to back up your website locally or restore from a backup.
	</p>
	<p>
		Speaking of not having access to the XHTML or HTML of the page, it seems pages built using the Wix system aren&apos;t even output as proper XHTML or HTML! Instead, they&apos;re output as JavaScript and loaded into a generic HTML template.
		The effect on accessibility is dire.
		No one with JavaScript disabled or with a Web browser that doesn&apos;t support JavaScript can load your Wix-powered websites! This problem alone, if nothing else, should convince you to avoid using Wix like the plague.
	</p>
</section>
<hr/>
<section id="menus">
	<nav>
		<ul>
			<li>
				<a href="#home">Home</a>
			</li>
			<li>
				<a href="#xhtml">No XHTML access</a>
			</li>
			<li>
				<a href="#javascript">Required JavaScript</a>
			</li>
			<li>
				<a href="#menus">Tall menus</a>
			</li>
			<li>
				<a href="#good-things">Good things about Wix</a>
			</li>
			<li>
				<a href="https://y.st./en/coursework/">Past coursework</a>
			</li>
		</ul>
	</nav>
	<h2>Tall menus</h2>
	<img src="/img/CC_BY-SA_4.0/y.st./coursework/CS2205/IMG_20170920_114658.jpg" alt="Maple seeds" class="framed-centred-image" width="800" height="480"/>
	<p>
		The Wix system assumes your browser window is of at least a certain size, and has hard-coded menu heights that are too tall.
		My monitor isn&apos;t that big.
		When I have my browser window maximised, as I usually do, I can&apos;t reach the bottom item of the right-side menu.
		I have to put my browser in full screen mode to reach it, which blocks me from accessing my other browser tabs, other applications, and my panel.
		(The panel is the Linux equivalent of the Windows taskbar, for those of you unfamiliar with Linux desktops.) The right-side menu is just too tall.
		I have this issue with several of the submenus as well.
		No Web element should have a hard-coded size.
		That&apos;s just too inflexible for dealing with the huge range of window sizes (and even monitor sizes) your website will be viewed through.
	</p>
</section>
<hr/>
<section id="good-things">
	<nav>
		<ul>
			<li>
				<a href="#home">Home</a>
			</li>
			<li>
				<a href="#xhtml">No XHTML access</a>
			</li>
			<li>
				<a href="#javascript">Required JavaScript</a>
			</li>
			<li>
				<a href="#menus">Tall menus</a>
			</li>
			<li>
				<a href="#good-things">Good things about Wix</a>
			</li>
			<li>
				<a href="https://y.st./en/coursework/">Past coursework</a>
			</li>
		</ul>
	</nav>
	<h2>Good things about Wix</h2>
	<img src="/img/CC_BY-SA_4.0/y.st./coursework/CS2205/IMG_20170920_114459.jpg" alt="Splotchy leaves" class="framed-centred-image" width="800" height="480"/>
	<p>
		I really don&apos;t like the Wix system in its current form, but I also don&apos;t like to point out only the negative aspects and not the positive aspects.
		Wix does have some positive qualities as well.
		For example, one of the assignment requirements was that we add a navigation menu to all pages of the site.
		Wix made it easy to ensure this menu was in the same place across every page.
		There&apos;s an option to simply tell Wix to add a given element to every page, so you don&apos;t have to place the element there by hand on each page separately and try to make sure the element lines up the same each time.
	</p>
	<p>
		If you purchase a subscription to Wix, you can also add a custom domain to your website.
		If you&apos;re doing anything long-term on the Internet, you should have your own domain for recognisability and portability.
	</p>
</section>
END
);
